-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OTG Test Update - RT 6.1 - LLDP neighbor verification change #1887
base: main
Are you sure you want to change the base?
OTG Test Update - RT 6.1 - LLDP neighbor verification change #1887
Conversation
Pull Request Functional Test Report for #1887 / 4a79fbaVirtual Devices
Hardware Devices
|
Pull Request Test Coverage Report for Build 12356678562Details
💛 - Coveralls |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The README suggests we need to change the structure of the test overall.
Reading it closely, it seems to imply that we need to specifically test with LLDP enabled before disabling it, and that we do not disable LLDP at the interface level for the 2nd test.
I am happy with that in a follow-up patch though, let's leave the re-opened bug open in that case though.
feature/lldp/otg_tests/core_lldp_tlv_population_test/core_lldp_tlv_population_test.go
Show resolved
Hide resolved
TestLLDPEnabled is failing in neighbor state verification: third_party/openconfig/featureprofiles/feature/lldp/otg_tests/core_lldp_tlv_population_test/core_lldp_tlv_population_test.go:288: Telemetry for Node port neighbor at /lldp/interfaces/interface[name=et-0/0/1]/neighbors/neighbor[id=02:00:22:01:01:01-00:00:00:00:00:01]:
|
Update please? |
This changes is required in order to correctly match the status of an LLDP neighbor based on it oc telemetry not configuration.
Resolves #587